-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
filebeat/module/{iis,o365}: Fix uri_parts ingest pipeline processor output wrong extension #38216
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
This pull request is now in conflicts. Could you fix it? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one comment.
Co-authored-by: subham sarkar <sarkar.subhams2@gmail.com>
💔 Build Failed
Failed CI StepsHistory
cc @muthu-mps |
💔 Build Failed
Failed CI StepsHistory
cc @muthu-mps |
💚 Build Succeeded
History
cc @muthu-mps |
💚 Build Succeeded
History
cc @muthu-mps |
💚 Build Succeeded
History
cc @muthu-mps |
💚 Build Succeeded
History
cc @muthu-mps |
Proposed commit message
This PR fixes the errors in the pipeline tests which generates incorrect values for the
extension
field ofuri_parts
processor. Bug fix done in Elasticsearch to remove the incorrect url.extension values from the uri_parts ingest pipeline processor. The affected beats module should remove this field from the generated sample documents. IIS error module and the o365 audit log modules are effected by this change.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
cd beats/filebeat
GENERATE=true TESTING_FILEBEAT_MODULES=iis,o365 mage -v pythonIntegTest
Related issues
This fixes the python integration tests failure reported in the below PR